v21.0.0-next.3

Compare Source

Breaking Changes

compiler-cli

• • Previously hidden type issues in host bindings may show up in your builds. Either resolve the type issues or set "typeCheckHostBindings": false in the angularCompilerOptions section of your tsconfig.

core

• The server-side bootstrapping process has been changed to eliminate the reliance on a global platform injector.

  Before:

  const bootstrap = () => bootstrapApplication(AppComponent, config);

  After:

  const bootstrap = (context: BootstrapContext) =>
    bootstrapApplication(AppComponent, config, context);

  A schematic is provided to automatically update main.server.ts files to pass the BootstrapContext to the bootstrapApplication call.

  In addition, getPlatform() and destroyPlatform() will now return null and be a no-op respectively when running in a server environment.

• • TypeScript versions less than 5.9 are no longer supported.

compiler-cli

core

migrations

v21.0.0-next.2

Compare Source

Breaking Changes

common

• (test only) - TestBed now provides a fake PlatformLocation
  implementation that supports the Navigation API. This may break some
  tests, though we have not observed any failures internally. You can revert to the
  old default for TestBed by providing the MockPlatformLocation from
  @angular/common/testing in your providers:
  {provide: PlatformLocation, useClass: MockPlatformLocation}

core

• (test only) - Using provideZoneChangeDetection in the
  TestBed providers would previously prevent TestBed from rethrowing
  errors as it should. Errors in the test will now be rethrown, regardless
  of the usage of provideZoneChangeDetection. Tests should be adjusted to
  prevent or account for these errors. As in previous major versions,
  this behavior can be disabled with rethrowApplicationErrors: false in
  configureTestingModule as a last resort.
• ignoreChangesOutsideZone is no longer available as an
  option for configuring ZoneJS change detection behavior.

platform-browser

• The deprecated ApplicationConfig export from @angular/platform-browser has been removed.
  Please import ApplicationConfig from @angular/core instead.

router

• Router navigations may take several additional
  microtasks to complete. Tests have been found to often be highly
  dependent on the exact timing of navigation completions with respect to
  the microtask queue. The most common fix for tests is to ensure all
  navigations have been completed before making assertions. On rare
  occasions, this can also affect production applications. This can be
  caused by multiple subscriptions to router state throughout the application,
  both of which trigger navigations that happened to not conflict with the
  previous timing.

upgrade

• UpgradeAdapter is no longer available. Use
  upgrade/static instead

common

compiler

core

forms

http

platform-browser

platform-server

router

upgrade